Knowledge sharing based on meeting information

ABSTRACT

Features are disclosed for automatically facilitating knowledge sharing using information collected during meetings. Collected information may include both the content and context of a meeting. The meeting content may comprise text collected by automatic speech recognition or entered manually at a user device. The meeting context may comprise information such as the identities of meeting participants and subject matter from a meeting agenda. The content and context information may be used to identify relevant topics for which knowledge is available, and the available knowledge may be presented to one or more of the meeting participants.

INCORPORATION BY REFERENCE TO ANY PRIORITY APPLICATIONS

Any and all applications for which a foreign or domestic priority claimis identified in the Application Data Sheet as filed with the presentapplication are hereby incorporated by reference under 37 CFR 1.57.

This application, is a continuation of U.S. patent application Ser. No.15/673,984, entitled “KNOWLEDGE SHARING BASED ON MEETING INFORMATION”and filed on Aug. 10, 2017, which is a continuation of U.S. patentapplication Ser. No. 13/893,215, entitled “KNOWLEDGE SHARING BASED ONMEETING INFORMATION” and filed on May 13, 2013, the disclosure of whichis incorporated herein by reference.

BACKGROUND

Many organizations, including businesses, government agencies, andnon-profit institutions, are constantly accumulating information relatedto their activities. Common sources of information may include, forexample, emails, intranet pages, memoranda, work product, manuals, andthe like. Useful knowledge may be revealed from this information bothimplicitly (e.g., by patterns in the information) and explicitly (e.g.,by a document that summarizes a particular activity of an organization).

Sharing knowledge between individuals within an organization may providea variety of benefits, including increased efficiency and improveddecision making. Accordingly, many organizations devote substantialresources to collecting and managing information of all sorts. Even whensubstantial and consistent effort is expended to distill and organizeknowledge from a large volume of information, e.g., by producing acomprehensive operations manual, the effort required to access theknowledge may prevent many people from taking advantage of it. Ofcourse, many organizations do not maintain any comprehensiverepositories of knowledge whatsoever, and in these organizations thebenefits of knowledge sharing are even more limited.

Several elements may be required to make use of shared knowledge, andincreasing the efficiency of any or all of these elements may increasethe benefits derived from such knowledge. Elements may include, forexample, (1) considering the possibility that shared knowledge existswhen faced with a particular problem; (2) identifying a source of suchknowledge; and (3) finding the desired knowledge within the source.

Ideally, knowledge will be provided at the moment it is needed. Ifknowledge is provided too early, its usefulness may not be apparent orit may be forgotten before it can be used. If knowledge is provided toolate, the need itself may be forgotten and more effort may be requiredto use the knowledge. Making access to shared knowledge more efficientalso makes it easier to provide knowledge at the moment it is mostuseful.

BRIEF DESCRIPTION OF THE DRAWINGS

Throughout the drawings, reference numbers may be re-used to indicatecorrespondence between referenced elements. The drawings are provided toillustrate example embodiments described herein and are not intended tolimit the scope of the disclosure.

FIG. 1 is a block diagram of an illustrative knowledge sharingenvironment including several devices for sharing knowledge based oninformation associated with a meeting.

FIG. 2 is a block diagram of an illustrative system for sharingknowledge based on meeting information.

FIG. 3 is a user interface diagram of an illustrative user deviceproviding sub-topic selection for knowledge sharing based on meetinginformation.

FIG. 4 is a user interface diagram of an illustrative user device forpresenting shared knowledge based on meeting information.

DETAILED DESCRIPTION Introduction

Generally described, the present disclosure relates to facilitatingknowledge sharing within an organization. Aspects of the presentdisclosure relate to automatically determining when shared knowledgerelevant to an ongoing meeting is available and presenting suchknowledge to meeting participants while it is relevant. For example, ifseveral individuals are participating in a meeting, a knowledge sharingsystem may use automatic speech recognition (ASR) to generate atranscript of any discussion that occurs. Relevant topics may beidentified from the transcript, and shared knowledge related to theidentified topics may be presented to one or more of the participants.Both the topics identified and the knowledge presented may depend oninformation obtained from the meeting, including, e.g., the identitiesof the participants, the purpose of the meeting, and the content of thediscussion. By minimizing the effort required to obtain shared knowledgeat relevant moments during the course of a meeting, features disclosedherein may facilitate efficient and competent action by individualswithin an organization.

Although aspects of the embodiments described in this disclosure willfocus, for the purpose of illustration, on features provided by acentral knowledge sharing system and various user devices, one skilledin the art will appreciate that the techniques disclosed herein may beapplied to any number of software processes or applications, implementedon any number of different hardware devices. In addition, the term“meeting,” as used herein, is a broad term and includes, withoutlimitation, seminars, speeches, informal discussions, and conversations.Further, although various aspects of the disclosure will be describedwith regard to illustrative examples and embodiments, one skilled in theart will appreciate that the disclosed embodiments and examples shouldnot be construed as limiting. Various aspects of the disclosure will nowbe described with regard to certain examples and embodiments, which areintended to illustrate but not limit the disclosure.

Knowledge Sharing Environment

Prior to describing embodiments of the knowledge sharing systems andmethods in detail, an example knowledge sharing environment in which thesystems and methods may be implemented will be described. FIG. 1illustrates a knowledge sharing environment including servers 150 andvarious user devices 112-118 communicating over a communication network140. The communication network 140 may be any wired network, wirelessnetwork, or combination thereof. In addition, the network 140 may be apersonal area network, local area network, wide area network, cablenetwork, satellite network, cellular telephone network, or combinationthereof. For example, the communication network 140 may be a publiclyaccessible network of linked networks, possibly operated by variousdistinct parties, such as the Internet. In some embodiments, thecommunication network 140 may be a private or semi-private network, suchas a corporate or university intranet. The communication network 140 mayinclude one or more wireless networks, such as a Global System forMobile Communications (GSM) network, a Code Division Multiple Access(CDMA) network, a Long Term Evolution (LTE) network, or some other typeof wireless network. Protocols and components for communicating via theInternet or any of the other aforementioned types of communicationnetworks are well known to those skilled in the art of computercommunications and thus, need not be described in more detail herein.

The user devices 112-118 can correspond to a wide variety of electronicdevices. In some embodiments, one or more user devices 112-118 arecomputing devices that include one or more processors and a memory whichmay contain software applications executed by the processors. Userdevices 112-118 may include displays for presenting information andmicrophones for capturing audio. In addition, the user devices 112-118may be configured with one or more wireless network antennae or wiredports to facilitate communication with other devices and with theknowledge sharing servers 150. The software of the user devices 112-118may include components for establishing communications over thecommunication network 140. In addition, the software may includeknowledge sharing applications which capture meeting audio forprocessing by an ASR engine, present transcripts generated from theaudio, and provide information on topics discussed in the meeting. Incertain embodiments, some or all of the user devices will receive textinput, in addition to or instead of audio input, e.g., via a physical orvirtual keyboard. Manually entered text may be combined withautomatically generated text from ASR to produce a unified transcript.

The user devices may include tablet computers, laptop computers, mobilephones, electronic book readers, personal audio players, personaldigital assistants, and the like. The user devices may also be builtspecifically for knowledge sharing. Different user devices in the sameknowledge sharing environment may include different hardware andsoftware. In some embodiments, multiple user devices may be integratedinto a single physical unit. For example, the user devices may compriseseveral screens and microphones built into a conference room table, allof which may be connected to a single computing device. In otherembodiments, multiple user devices may be located remotely from oneanother.

In addition to devices for individual users, such as user devices112-118, the knowledge sharing environment may include devices for groupuse, such as group device 130. While user devices 112-118 may presentknowledge that is relevant to any individual meeting participant, groupdevice 130 may only present knowledge that is likely to be relevant tomultiple participants. In some embodiments, multiple group devices manybe provided to accommodate different participant groups, particularly inmeetings with large numbers of participants. For example, one groupdevice may be configured for use by members of a marketing department,and another group device may be configured for use by members of anengineering department. When multiple group devices are used, theknowledge presented on each device may vary depending on what is deemedrelevant to each participant group.

In general, group device 130 may comprise hardware and software similarto user devices 112-118, although various aspects may be modified tosupport shared use by multiple individuals. For example, group device130 may comprise a larger display area, additional microphones, etc.Although group device 130 is depicted as a projector in FIG. 1, anysuitable display may be used. In addition to a display, group device 130may include additional hardware to perform computation and otherfunctions similar to those of user devices 112-118.

The knowledge sharing servers 150 illustrated in FIG. 1 may correspondto one or more computing devices configured to facilitate automatedknowledge sharing via the user devices 112-118 and/or group device 130.For example, the servers 150 may include one or more processors and acomputer storage or memory which contains software applications ormodules executed by the processors. The functionality provided by theservers 150 can include receiving audio data from the user devices,performing ASR on the audio to generate a meeting transcript,identifying topics from the transcript, and providing access to sharedknowledge related to the identified topics. In some embodiments, theservers 150 may correspond to a logical association of one or morecomputing devices, such as an ASR server for recognizing speech, adatabase server for storing information about available knowledge, andan application server for managing interactions with the user devices.In some embodiments, the features and services provided by the serversmay be implemented as web services consumable via the communicationnetwork 120. In further embodiments, the shared consumption managementsystem 102 is provided by one more virtual machines implemented in ahosted computing environment. The hosted computing environment mayinclude one or more rapidly provisioned and released computingresources, which computing resources may include computing, networkingand/or storage devices. A hosted computing environment may also bereferred to as a cloud computing environment.

In some embodiments, the knowledge sharing environment may includeadditional or fewer components than those illustrated in FIG. 1. Forexample, the networked content consumption environment may not includeseparate servers 150. Rather, the features of the servers 150 may beimplemented by one or more of the user devices. In another example, aload balancer may be included to allocate computing tasks among theservers 150.

Turning now to FIG. 2, an illustrative knowledge sharing system will bedescribed. The knowledge sharing system of FIG. 2 may comprise a userdevice 210, which may correspond to one of the user devices 112-118 ofFIG. 1, and a server 220, which may correspond to one of the servers 150of FIG. 1. The user computing device 210 and server 220 may each beembodied in a plurality of components, each executing an instance of therespective user computing device 210 and server 220. Each of the usercomputing device 210 and the server 220 may include a network interface,memory, processing unit, and non-transitory computer-readable mediumdrive, all of which may communicate with each other by way of acommunication bus. Moreover, a processing unit may itself be referred toas a computing device. The network interface may provide connectivityover the network 140 and/or other networks or computer systems. Theprocessing unit may communicate to and from memory containing programinstructions that the processing unit executes in order to operate theuser computing device 210 and server 220. The memory generally includesRAM, ROM, and/or other persistent and/or auxiliary non-transitorycomputer-readable storage media.

As illustrated in FIG. 2, the user device 210 may execute an audioprocessing module 212, a transcript presentation module 204, a topicselection module 206, and a knowledge presentation module 218, each ofwhich may be stored in memory of the user device 210. The server 220 mayexecute a speech recognition module 222, a topic identification module224, and a knowledge retrieval module 226, each of which may be storedin memory of the server 220. As described earlier with respect to thecorresponding devices of FIG. 1, the functionality of the user device210 and the server 220 may be rearranged. For example, speechrecognition module 222 may be implemented on user device 210 rather thanserver 220.

In addition to various modules of user device 210 and server 220, theknowledge sharing system of FIG. 2 also includes context store 230 andknowledge store 240, both of which may comprise multiple data storeswith varying structure and content. Context store 230 and knowledgestore 240 may be remote from the server 220. Additionally, the knowledgesharing system may include additional or fewer modules and/or datastores than those illustrated in FIG. 2.

Knowledge store 240 may comprise various primary sources from whichknowledge may be obtained, such as document management systems, emailrepositories, wikis, project management databases, operations manuals,dictionaries, glossaries, etc. In addition, knowledge store 240 maycomprise reference sources for organizing, summarizing, or structuringthe contents of the primary sources. For example, reference sources maycomprise search indexes, lists of topics, and document clusters, any orall of which may be automatically generated from the primary sources.

Context store 230 may comprise information that can be used tofacilitate automated knowledge sharing based on the context of ameeting. As described below, context information may be used to improveaccuracy and relevance in various parts of the knowledge sharing system.Context store 230 may include specific information about thecircumstances of a meeting, such as the identities of meetingparticipants, the date and time of the meeting, or the meeting agenda.In addition, context store 230 may include supplemental informationrelated to the specific circumstances, such as job titles,responsibilities, documents previously distributed, and recent emails ofthe meeting participants. This supplemental information may overlap withthe contents of knowledge store 240, but may be used differently. Forexample, supplemental information in the form of one or more emails maybe used to determine which meeting participants are already familiarwith a particular topic. Knowledge regarding the particular topic maythen be shared only with participants who are not yet familiar with it.

Example interactions between the various components of the knowledgesharing system will now be described. As noted above, the knowledgesharing system may be used to transcribe a discussion that occursbetween several participants during a meeting. Accordingly, user device210 may be configured to capture audio when a participant speaks. Thecaptured audio signal may be used for ASR, as described below. Ifmultiple user devices are present in a meeting, each device may beconfigured to only capture audio corresponding to the speech of aparticular participant or subset of participants. For example, if eachparticipant has a separate device, then the device belonging to eachparticipant may capture audio for that participant only. Alternatively,all of the devices may capture audio for all of the participants, andaudio data from multiple devices may be combined to produce better ASRresults. If multiple audio signals are provided by devices in differentlocations relative to a particular speaker, the accuracy of ASR resultsproduced from the audio signals may be improved by selecting the singledevice with the best audio quality for a particular portion of anutterance, or by determining the most likely content of the utterance inlight of the combination of captured audio signals.

Audio processing module 212 may receive an audio signal captured by userdevice 210 and extract data for use in ASR. An ASR process may includeseveral “front-end” elements, such as speech detection and featureextraction. Any or all of these elements may be performed by audioprocessing module 212. Alternatively, some or all of these elements maybe performed by speech recognition module 222 of server 220. If theaudio processing module performs the feature extraction, the audio datatransmitted to server 220 may include feature vectors, which measurecertain aspects of an audio signal that are useful for ASR. If thefeature extraction is performed by the speech recognition moduleinstead, then the transmitted audio data may comprise a digital audiostream.

The audio data, whether it comprises feature vectors, an audio stream,or other data, is sent by audio processing module 212 to speechrecognition module 222. The speech recognition module performs ASR usingthe audio data, producing a transcript of any words spoken by meetingparticipants. Speech recognition module 222 may also identify differentspeakers, and label the transcript to specify which participant spokewhich words. In some embodiments, the identity of a particular speakermay be provided by user device 210, and transmitted to speechrecognition module 222 along with the audio data. As speech istranscribed, the resulting text is provided to topic identificationmodule 224.

Topic identification module 224 identifies topics for which sharedknowledge is available based on the transcribed text, and informationfrom context store 230. Annotations may be added to the transcript toindicate the availability of shared knowledge on a particular topic. Forexample, words in the transcript that describe a relevant topic may beunderlined, highlighted, or otherwise set apart. Alternatively, if atopic is identified as relevant but the words in the transcript do notappropriately describe it, an annotation may be added between lines ofthe transcript or in a margin. Although topic identification module 224may distinguish between multiple types of annotations, such as inlineand marginal, the manner in which such annotations are actuallypresented may be determined by transcript presentation module 214,described below. Accordingly, when the annotated transcript isconstructed and transmitted, the annotations therein may be representedsemantically rather than visually, e.g., using Extensible MarkupLanguage (XML).

Meeting topics may be identified from a transcript in a variety of ways.In some embodiments, topic identification may be fully automatic, whilein other embodiments there may be some manual involvement. In the caseof manual involvement, a user may prepare a list of topics, keywords, orother metadata, and embed this metadata in an agenda, presentation, orother form of meeting materials made available to topic identificationmodule 224. For example, a user may provide a list of topics in the“Notes” section of one or more slides in a Microsoft PowerPointpresentation, and as each slide is presented at a meeting, the topicslisted in the slide's “Notes” section may be annotated in the meetingtranscript. Specific topics may also be provided by input to a userdevice, which may transmit the topic directly to topic identificationmodule 224, or to knowledge retrieval module 226 (described below).

In the case of automated topic identification, the transcript may beanalyzed to identify one or more relevant attributes, and the identifiedattributes may be used to search for available topics. The topic searchmay also rely on information from context store 230, as noted above. Inone example, a list of available topics may be provided by knowledgestore 240. An index may be provided as well, to associate one or morekeywords with each available topic from the list. Both the list and theindex may be updated regularly based on new information generated by theorganization. During a meeting, words from the transcript may becompared with keywords from the index to identify potentially relevanttopics from the list. These potentially relevant topics may be filteredbased on information from context store 230, to determine which topicswill actually be annotated in the transcript.

In the foregoing example, the attributes identified from the transcriptare the words of the transcript themselves. In some embodiments,however, more complex attributes may be used. Complex attributes may becalculated, looked up, or otherwise determined from the words of thetranscript in any number of ways. Specifically, attributes may includeany text, number, or other data value that is likely to be correlatedwith the relevance of particular topics. In addition, while theforegoing example contemplated the use of context information to filterpotentially relevant topics after they are identified from a set ofattributes, context information may also be incorporated into theattributes themselves and used to identify topics from an indexdirectly.

In some embodiments, different topics may be identified and annotatedfor different users. The specific topics that are identified andannotated for a particular user may be based on, e.g., contextinformation about the user or other meeting participants, or a set ofsecurity permissions. For example, topic identification module 224 maydetermine that a certain topic is more or less relevant for a particularuser based on the supplemental information from context store 230,described above. The supplemental information may include emails fromthe user indicating that the user is already familiar with availableknowledge on a particular topic, in which case the topic may not beannotated in a transcript transmitted to the user's device.

Topics may also be identified and annotated on the basis of contextinformation about meeting participants other than the particular user towhom the topics are presented. For example, if a meeting is being led bya member of an engineering team, technical topics may be assigned ahigher relevance for some or all meeting participants. Alternatively, ifa meeting is being led by a high-level executive, topics related tobusiness strategy may be assigned a higher relevance. As describedbelow, the factors that influence topic identification may alsoinfluence the knowledge results that are produced when a topic isselected.

With respect to security permissions, certain users may be preventedfrom accessing knowledge related to certain topics, e.g., because theknowledge is derived from sources that the user is does not havepermission to view. Security permissions may be specified manually forcertain types of sources and automatically for others. For example, allusers within an organization may have access to knowledge derived fromwiki pages, but knowledge derived from emails may be more tightlycontrolled by security rules that are based on each email's originalrecipients.

As topics are identified for a particular portion of the transcript,topic identification module 224 may transmit the resulting annotatedtranscript portion to user device 210. At the user device, topicselection module 216 may receive the annotated transcript portion andpresent it to a user. Example user interfaces for presenting annotatedtranscripts are described below with respect to FIGS. 3 and 4.Interfaces like these may be presented by topic selection module 216,and used to receive input specifying a topic of interest. The resultingtopic selection may be transmitted back to server 220, and received byknowledge retrieval module 226.

Knowledge retrieval module 226 may generate knowledge results for aselected topic. These results may comprise, e.g., a summary, digest, orother collection of knowledge relating to the selected topic, based ondata retrieved from knowledge store 240. In some embodiments, knowledgeresults for a particular topic may include references to related topics.Knowledge retrieval module may also generate results for topics that areselected automatically, without user input. Automatic topic selectionmay be based on, for example, estimated relevance of selected topics toone or more users.

The knowledge results generated by knowledge retrieval module 226 maycomprise information excerpted from one or more primary sources withinknowledge store 240. These excerpts may be harmonized to varyingdegrees. For example, excerpts from multiple sources may beautomatically integrated into a coherent whole, e.g., comprisingsubstantially continuous prose. Alternatively, a single primary sourcemay contain an excerpt suitable for presentation by itself, such as awiki page. Excerpts may also be combined into a list, with separateentries for each excerpt. Knowledge results for different topics may usedifferent approaches for selecting and combining source information.With any approach, the excerpts from the primary sources may includeinformation in various mediums, such as text, images, videos, etc.

Knowledge results for some or all available topics may be partially orcompletely generated ahead of time. For example, a summary of theknowledge available for a particular topic may be generated and storedin completed form in knowledge store 240. Then, if the topic isselected, whether automatically or by a user, knowledge retrieval module226 may provide a result for the topic simply by accessing thepre-generated summary. As an example of partially pre-generated results,knowledge store 240 may store associations that link a particular topicwith relevant excerpts from primary sources. Then, if the topic isselected, knowledge retrieval module 226 may generate a result bylisting the linked excerpts along with the corresponding primarysources.

Knowledge results, much like the topic annotations, may vary betweenusers. Specifically, certain information may be included or excludedwhen a knowledge result is generated based on security permissionsassociated with the underlying sources, or with particular topics. Inaddition, knowledge results on the same topic may vary between usersdepending on what each user is likely to be familiar with and what eachuser is likely to be interested in, as determined from information incontext store 230.

As results are generated, they may be transmitted to user device 210.The results may be received by knowledge presentation module 218, andpresented to one or more users. Example interfaces for such presentationare described below with respect to FIGS. 3 and 4.

As described previously, both topic identification module 224 andknowledge retrieval module 226 may rely on topic lists, indexes, andother reference sources. These reference sources may allow server 220 toidentify relevant topics and retrieve relevant knowledge in real time asa meeting transcript is generated. Reference sources may be generatedand updated in accordance with a wide variety of techniques, many ofwhich are known to person skilled in the art of natural languageprocessing. Relevant techniques may include topic segmentation,automatic summarization, named entity recognition, and terminologyextraction.

In one example, pages on an organizational intranet may include titlesthat are explicitly designated as such, e.g., according to a database orXML schema. The knowledge sharing system may compile a topic list inpart by creating topics for each of the titles. The system may alsoidentify key words from each intranet page, e.g., based on the frequencywith which they occur. The identified key words may be stored in anindex and associated with the topic that corresponds to the page. Thesekey words may be used to identify topics in a meeting transcript, asdescribed earlier in this disclosure.

Lists, indexes, and other reference sources may need to be updated asinformation is generated or modified. Therefore, in some embodiments,the knowledge sharing system may maintain a database of dependenciesbetween reference sources and primary sources, or portions thereof. Wheninformation in a primary source is modified, any reference sources thatdepend on that primary source may be updated accordingly.

Meeting transcripts themselves may constitute an important source ofknowledge and context. Accordingly, information from meeting transcriptsmay be included in context store 230 or knowledge store 240. Inparticular, context store 230 may include the transcript of a meetingthat is underway, and the text in the transcript may be used to improvetopic identification, automated topic selection, and knowledge retrievalas the meeting goes on. For example, at the beginning of the topicidentification module 224 may lack sufficient information todefinitively identify certain topics that are being discussed. As themeeting transcript grows, however, more context may be available andadditional topics may be identified.

Meeting transcripts are also a source of knowledge. Accordingly,transcripts of past meetings may be included in knowledge store 240. Insome situations, meeting transcripts may not be stored permanently(e.g., because they contain sensitive information), but may be used toimprove existing reference sources. For example, a meeting transcriptmay be used to identify associations between related topics, and theseassociations may be added to a table in knowledge store 240 before themeeting transcript is deleted. Of course, meeting transcripts may alsobe used to improve reference sources even if they are also stored infull-text form.

Interfaces For Transcript Presentation, Topic Selection, and KnowledgePresentation

As explained above, user device 210 of FIG. 2 may present transcripts,receive topic selections from a user, and present knowledge results forselected topics. User interface 300, illustrated in FIGS. 3 and 4,supports each of these operations, as described below. User interface300 may be implemented e.g., as a web application or native applicationon user devices 112-118 of FIG. 1.

With reference to FIG. 3, user interface 300 may include transcriptpanel 310 and topic panel 320. Transcript panel 310 may display anannotated transcript received from server 220. As successive portions ofthe annotated transcript are received, older portions may scroll out ofview automatically to make room for newer ones. In some embodiments,user interface 300 may include a button or other input means totemporarily pause the automatic scrolling. User interface 300 may alsobe configured to pause automatic scrolling when input is predicted intranscript panel 310, e.g., based on movements of a mouse cursor withinthe panel.

The annotated transcript displayed in transcript panel 310 may includewords 314 associated with a particular meeting participant. The wordsmay be labeled with an identifier of the participant who spoke or wrotethe words, such as name 312. The identifier may also comprise, e.g.,initials, a portrait, or a graphical avatar. The annotated transcriptmay also include annotations associated with particular topics, such asannotation 316. Annotations may be presented in various ways, in orderto draw a user's attention and invite input such as a finger tap ormouse click. For example, words corresponding to a topic may beunderlined, highlighted, or otherwise emphasized. Input directed by auser to a particular annotation may be interpreted as a selection of thecorresponding topic.

When a user selects a topic displayed in transcript panel 310, knowledgeresults corresponding to the topic may be displayed in topic panel 320.Words identifying the topic and/or the knowledge results may be providedin header 322, and the knowledge results themselves may appear below. Ifthe topic is broad or ambiguous, however, it may be associated withseveral subtopics or possible meanings. Accordingly, a menu may beprovided to allow the user to select one of the subtopics or possiblemeanings, in order to narrow the scope of the knowledge results beforethey are presented. Thus, for example, when the user selects the topic“Project X” by clicking annotation 316, the topic name may be providedin header 322 and the subtopics of Project X may be listed in menu 324.The results of selecting one of the subtopics from menu 324 are depictedin FIG. 4.

As shown in FIG. 4, if the user selects a subtopic from menu 324,heading 322 may be updated to display the name of the subtopic. Inaddition, knowledge results associated with the selected subtopic may bedisplayed below the heading. For example, if the subtopic “Goals ofProject X” is selected, heading 322 may be updated as shown in FIG. 4,and knowledge results 402 may be presented.

As described previously with respect to FIG. 2, some topics may beselected automatically, without specific input from a user. In certainembodiments, knowledge results for automatically selected topics will bepresented in the same manner as knowledge results for user-selectedtopics. For example, knowledge results for an automatically selectedtopic may be presented immediately below heading 322 in topic panel 320of FIGS. 3 and 4. Alternatively, some or all automatically selectedtopics may be presented in a different manner.

In some embodiments, a knowledge result for an automatically selectedtopic may be presented compactly in notification box 404. Such compactpresentation may allow knowledge results for an automatically selectedtopic to be presented with less risk of annoyance to the user, e.g.,because knowledge results for incorrectly selected topics may be lessconspicuous, and may be less likely to interfere with a user's readingof knowledge results for a manually selected topic. For addedconvenience, notification box 404 may be configured to disappearautomatically after a specific period of time unless input is detectedtherein. If the user is interested in obtaining more information aboutan automatically selected topic, button 406 may be used to displaydetailed knowledge results in the area below heading 322.

Whether knowledge results are displayed in notification box 404 orelsewhere, the timing of automatic topic selection may be configured toavoid interfering with the presentation of knowledge results formanually selected topics. For example, automatic topic selection may beavoided when a user has recently made a manual selection, or inputcollected at the user device (e.g., scrolling) suggests that the user iscurrently reviewing knowledge results for a manually selected topic. Insome embodiments, manually selected topics may be presented in the styleof notification box 404, particularly if the knowledge results for theselected topic are concise.

Although the foregoing disclosure describes a system in which meetingtranscripts are generated and displayed on various devices, someembodiments may not include such transcripts. For example, rather thanproviding a full annotated transcript to a user device, some embodimentsmay simply provide a list of topics that are identified from a meetingdiscussion. A topic list may scroll automatically, like an annotatedtranscript, so that new topics are visible as they are added to thelist. Using a topic list in place of an annotated transcript may beadvantageous for user devices with small screens, such as mobile phones.In addition, some interfaces may support both annotated transcripts andtopic lists. For example, a transcript may be hidden or minimized whenknowledge results are displayed, in order to provide additional screenspace for viewing the knowledge results. A topic list may be providedwhen the transcript is hidden so that new topics can continue to bedisplayed.

Terminology

Depending on the embodiment, certain acts, events, or functions of anyof the processes or algorithms described herein can be performed in adifferent sequence, can be added, merged, or left out altogether (e.g.,not all described operations or events are necessary for the practice ofthe algorithm). Moreover, in certain embodiments, operations or eventscan be performed concurrently, e.g., through multi-threaded processing,interrupt processing, or multiple processors or processor cores or onother parallel architectures, rather than sequentially.

The various illustrative logical blocks, modules, routines, andalgorithm elements described in connection with the embodimentsdisclosed herein can be implemented as electronic hardware, computersoftware, or combinations of both. To clearly illustrate thisinterchangeability of hardware and software, various illustrativecomponents, blocks, modules, elements and steps have been describedabove generally in terms of their functionality. Whether suchfunctionality is implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem. The described functionality can be implemented in varying waysfor each particular application, but such implementation decisionsshould not be interpreted as causing a departure from the scope of thedisclosure.

The elements of a method, process, routine, or algorithm described inconnection with the embodiments disclosed herein can be embodieddirectly in hardware, in a software module executed by a processor, orin a combination of the two. A software module can reside in RAM memory,flash memory, ROM memory, EPROM memory, EEPROM memory, registers, harddisk, a removable disk, a CD-ROM, or any other form of a non-transitorycomputer-readable storage medium. An exemplary storage medium can becoupled to the processor such that the processor can read informationfrom, and write information to, the storage medium. In the alternative,the storage medium can be integral to the processor. The processor andthe storage medium can reside in an ASIC. The ASIC can reside in a userterminal. In the alternative, the processor and the storage medium canreside as discrete components in a user terminal.

Conditional language used herein, such as, among others, “can,” “could,”“might,” “may,” “e.g.,” and the like, unless specifically statedotherwise, or otherwise understood within the context as used, isgenerally intended to convey that certain embodiments include, whileother embodiments do not include, certain features, elements and/orsteps. Thus, such conditional language is not generally intended toimply that features, elements and/or steps are in any way required forone or more embodiments or that one or more embodiments necessarilyinclude logic for deciding, with or without author input or prompting,whether these features, elements and/or steps are included or are to beperformed in any particular embodiment. The terms “comprising,”“including,” “having,” and the like are synonymous and are usedinclusively, in an open-ended fashion, and do not exclude additionalelements, features, acts, operations, and so forth. Also, the term “or”is used in its inclusive sense (and not in its exclusive sense) so thatwhen used, for example, to connect a list of elements, the term “or”means one, some, or all of the elements in the list.

Disjunctive language such as the phrase “at least one of X, Y, or Z,”unless specifically stated otherwise, is otherwise understood with thecontext as used in general to present that an item, term, etc., may beeither X, Y, or Z, or any combination thereof (e.g., X, Y, and/or Z).Thus, such disjunctive language is not generally intended to, and shouldnot, imply that certain embodiments require at least one of X, at leastone of Y, or at least one of Z to each be present.

While the above detailed description has shown, described, and pointedout novel features as applied to various embodiments, it can beunderstood that various omissions, substitutions, and changes in theform and details of the devices or algorithms illustrated can be madewithout departing from the spirit of the disclosure. As can berecognized, certain embodiments of the inventions described herein canbe embodied within a form that does not provide all of the features andbenefits set forth herein, as some features can be used or practicedseparately from others. The scope of certain inventions disclosed hereinis indicated by the appended claims rather than by the foregoingdescription. All changes which come within the meaning and range ofequivalency of the claims are to be embraced within their scope.

1. A system comprising: a data storage medium configured to store userprofiles; and one or more computer hardware processors in communicationwith the data storage medium, wherein the one or more computer hardwareprocessors are configured to execute computer-executable instructions toat least: receive, from a first device, audio data corresponding tospoken dialogue involving two or more participants, wherein a firstparticipant of the two or more participants is associated with a firstuser profile and a second participant of the two or more participants isassociated with a second user profile; generate, with automatic speechrecognition, a transcript of the spoken dialogue from the audio data,wherein the transcript comprises a plurality of words; identify akeyword associated with the attribute of the first participant;determine that the keyword corresponds to at least one word of theplurality of words; in response to determining that the keywordcorresponds to at least one word of the plurality of words, identify,from a plurality of topics, a first topic associated with the keyword;receive an electronic item associated with the first topic; and causepresentation, via a user interface on the first device, of a visualrepresentation of the electronic item.
 2. The system of claim 1, whereinthe one or more computer hardware processors are configured to executefurther computer-executable instructions to at least: receive, from thefirst device, manually entered text; determine that a second keywordcorresponds to at least one word from the manually entered text; inresponse to determining that the second keyword corresponds to at leastone word from the manually entered text, identify, from the plurality oftopics, a second topic associated with the second keyword; receive adata entry associated with the second topic; and cause presentation, viathe user interface on the first device, of a visual representation ofthe data entry.
 3. The system of claim 1, wherein the electronic itemincludes an email, and wherein the one or more computer hardwareprocessors are configured to execute further computer-executableinstructions to at least: determine a security permission based at leaston an original recipient of the email; identify a third user profilethat is allowed access to the email according to the securitypermission; and send data from the email to a third device associatedwith the third user profile.
 4. The system of claim 1, whereinpresentation of the visual representation of the electronic item in theuser interface occurs during a meeting including the two or moreparticipants.
 5. The system of claim 1, wherein the first device isassociated with the first user profile, wherein the one or more computerhardware processors are configured to execute furthercomputer-executable instructions to at least: determine to exclude theelectronic item from the second participant based at least in part onthe second user profile; and exclude presentation of the electronic itemfrom a second device associated with the second user profile.
 6. Thesystem of claim 1, wherein the first device is associated with the firstuser profile, wherein the one or more computer hardware processors areconfigured to execute further computer-executable instructions to atleast: determine an estimated lack of relevance for the first topicbased at least in part on the second user profile; and in response todetermining an estimated lack of relevance for the first topic,excluding presentation of the electronic item associated with the firsttopic from a second device associated with the second user profile. 7.The system of claim 1, wherein the one or more computer hardwareprocessors are configured to execute further computer-executableinstructions to at least: estimate a level of relevance of the firsttopic for the first participant; and determine that the level ofrelevance satisfies a threshold.
 8. The system of claim 1, wherein theone or more computer hardware processors are configured to executefurther computer-executable instructions to at least: receiveelectronically stored data associated with the first topic; generate asummary of the electronically stored data; and cause presentation, viathe user interface on the first device, of the summary.
 9. The system ofclaim 1, wherein the one or more computer hardware processors areconfigured to execute further computer-executable instructions to atleast: identify, from the plurality of topics, a second topic associatedwith the keyword; and cause presentation, via the user interface on thefirst device, of the first topic and the second topic.
 10. The system ofclaim 9, wherein presentation, via the user interface on the firstdevice, of the second topic includes a selectable indication, the one ormore computer hardware processors are configured to execute additionalcomputer-executable instructions to at least: receive, from the firstdevice, input data representing a selection of the selectableindication; and in response to receiving the input data, causepresentation, via the user interface on the first device, of a visualrepresentation of a second electronic item associated with the secondtopic.
 11. A computer-implemented method comprising: receiving, from afirst device, audio data corresponding to spoken dialogue involving twoor more participants, wherein a first participant of the two or moreparticipants is associated with a first user profile and a secondparticipant of the two or more participants is associated with a seconduser profile; generating, with automatic speech recognition, atranscript of the spoken dialogue from the audio data, wherein thetranscript comprises a plurality of words; identifying a keywordassociated with the first participant; determining that the keywordcorresponds to at least one word of the plurality of words; in responseto determining that the keyword corresponds to at least one word of theplurality of words, identifying, from a plurality of topics, a firsttopic associated with the keyword; receiving an electronic itemassociated with the first topic; and causing presentation, via a userinterface on the first device, of a visual representation of theelectronic item.
 12. The computer-implemented method of claim 11 furthercomprising: receiving, from the first device, manually entered text; anddetermining that the keyword corresponds to the manually entered text.13. The computer-implemented method of claim 11, wherein the electronicitem includes an email, the computer-implemented method furthercomprising: determining a security permission based at least on anoriginal recipient of the email; identifying a third user profile thatis allowed access to the email according to the security permission; andsending data from the email to a third device associated with the thirduser profile.
 14. The computer-implemented method of claim 11, whereinpresentation of the visual representation of the electronic item in theuser interface occurs during a meeting including the two or moreparticipants.
 15. The computer-implemented method of claim 11, whereinthe first device is associated with the first user profile, thecomputer-implemented method further comprising: determining to excludethe electronic item from the second participant based at least in parton the second user profile; and excluding presentation of the electronicitem from a second remote device associated with the second userprofile.
 16. The computer-implemented method of claim 11, wherein thefirst device is associated with the first user profile, thecomputer-implemented method further comprising: determining an estimatedlack of relevance for the first topic based at least in part on thesecond user profile; and in response to determining an estimated lack ofrelevance for the first topic, excluding presentation of the electronicitem associated with the first topic from a second device associatedwith the second user profile.
 17. The computer-implemented method ofclaim 11 further comprising: estimating a level of relevance of thefirst topic for the first participant; and determining that the level ofrelevance satisfies a threshold.
 18. The computer-implemented method ofclaim 11 further comprising: receiving electronically stored dataassociated with the first topic; generating a summary of theelectronically stored data; and causing presentation, via the userinterface on the first device, of the summary.
 19. Thecomputer-implemented method of claim 11 further comprising: identifying,from the plurality of topics, a second topic associated with thekeyword; and causing presentation, via the user interface on the firstdevice, of the first topic and the second topic.
 20. Thecomputer-implemented method of claim 19, wherein presentation, via theuser interface on the first device, of the second topic includes aselectable indication, the computer-implemented method furthercomprising: receiving, from the first device, input data representing aselection of the selectable indication; and in response to receiving theinput data, causing presentation, via the user interface on the firstdevice, of a visual representation of a second electronic itemassociated with the second topic.